지금 시작

스크립트에서 "THE SCRIPT"에 대해 찾기

120x ticker screener (composite tickers)In specific circumstances, it is possible to extract data, far above the 40 `request.*()` call limit for 1 single script . The following technique uses composite tickers . Changing tickers needs to be done in the code itself as will be explained further.           ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ 🔶 PRINCIPLE         Standard example:   c1 = request.security('MTLUSDT' , 'D', close)         This will give the close value from 1 ticker (MTLUSDT); c1 for example is 1.153         Now let's add 2 tickers to MTLUSDT; XMRUSDT and ORNUSDT with, for example, values of 1.153 (I), 143.4 (II) and 0.8242 (III) respectively.         Just adding them up 'MTLUSDT+XMRUSDT+ORNUSDT' would give 145.3772 as a result, which is not something we can use...         Let's multiply ORNUSDT by                  100 ->            14340         and   multiply MTLUSDT  by 1000000000 -> 1153000000                 (from now, 10e8 will be used instead of 1000000000)         Then we make the sum.         When we put this in a security call (just the close value) we get:   c1 = request.security('MTLUSDT*10e8+XMRUSDT*100+ORNUSDT', 'D', close)         'MTLUSDT*10e8+XMRUSDT*100+ORNUSDT' -> 1153000000 + 14340 + 0.8242 = 1153014340.8242 (a)         This (a) will be split later on, for example:         1153014330.8242 / 10e8 = 1.1530143408242 -> round -> in this case to 1.153 (I), multiply again by 10e8 -> 1153000000.00 (b)         We subtract this from the initial number:             1153014340.8242   (a)          - 1153000000.0000   (b)           –––––––––––––––––                        14340.8242   (c)         Then -> 14340.8242 / 100 = 143.408242 -> round -> 143.4 (II) -> multiply -> 14340.0000 (d)          -> subtract             14340.8242   (c)          - 14340.0000   (d)           ––––––––––––                      0.8242   (III)         Now we have split the number again into 3 tickers: 1.153 (I), 143.4 (II) and 0.8242 (III)           ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ In this publication the function compose_3_() will make a composite ticker of 3 tickers, and the split_3_() function will split these 3 tickers again after passing 1 request.security() call. In this example: t46 = 'BINANCE:MTLUSDT', n46 = 10e8 , r46 = 3, t47 = 'BINANCE:XMRUSDT', n47 = 10e1, r47 = 1, t48 = 'BINANCE:ORNUSDT', r48 = 4 // T16 ••• T16= compose_3_(t48, t47, n47, t46, n46) ••• = request.security(T16, res, ) ••• = split_3_(c16, n46, r46, n47, r47, r48) 🔶 CHANGING TICKERS If you need to change tickers, you only have to change the first part of the script, USER DEFINED TICKERS Back to our example, at line 26 in the code, you'll find: t46 = 'BINANCE:MTLUSDT', n46 = 10e8 , r46 = 3, t47 = 'BINANCE:XMRUSDT', n47 = 10e1, r47 = 1, t48 = 'BINANCE:ORNUSDT', r48 = 4 // T16 ( t46 , T16 ,... will be explained later) You need to figure out how much you need to multiply each ticker, and the number for rounding, to get a good result. In this case: 'BINANCE:MTLUSDT', multiply number = 10e8, round number is 3 (example value 1.153) 'BINANCE:XMRUSDT', multiply number = 10e1, round number is 1 (example value 143.4) 'BINANCE:ORNUSDT', NO multiply number, round number is 4 (example value 0.8242) The value with most digits after the decimal point by preference is placed to the right side (ORNUSDT) If you want to change these 3, how would you do so? First pick your tickers and look for the round values, for example: 'MATICUSDT', example value =   0.5876 -> round -> 4 'LTCUSDT'    , example value = 77.47      -> round -> 2 'ARBUSDT'    , example value =   1.0231 -> round -> 4 Value with most digits after the decimal point -> MATIC or ARB, let's pick ARB to go on the right side, LTC at the left of ARB, and MATIC at the most left side. -> 'MATICUSDT', LTCUSDT', ARBUSDT' Then check with how much 'LTCUSDT' and 'MATICUSDT' needs to be multiplied to get this: 5876 0 7747 0 1.0231 'MATICUSDT' -> 10e10 'LTCUSDT'      -> 10e3 Replace: t46 = 'BINANCE:MTLUSDT', n46 = 10e8 , r46 = 3, t47 = 'BINANCE:XMRUSDT', n47 = 10e1, r47 = 1, t48 = 'BINANCE:ORNUSDT', r48 = 4 // T16 -> t46 = 'BINANCE:MATICUSDT', n46 = 10e10 , r46 = 4, t47 = 'BINANCE:LTCUSDT', n47 = 10e3, r47 = 2, t48 = 'BINANCE:ARBUSDT', r48 = 4 // T16 DO NOT change anything at t46, n46,... if you don't know what you're doing! Only  • tickers ('BINANCE:MTLUSDT', 'BINANCE:XMRUSDT', 'BINANCE:ORNUSDT', ...),  • multiply numbers (10e8, 10e1, ...) and  • round numbers (3, 1, 4, ...) should be changed. There you go! 🔶 LIMITATIONS 🔹 The composite ticker fails when 1 of the 3 isn't in market in the weekend, while the other 2 are.      That is the reason all tickers are crypto. I think it is possible to combine stock,... tickers, but they have to share the same market hours. 🔹 The number cannot be as large as you want, the limit lays around 15-16 digits.      This means when you have for example 123, 45.67 and 0.000000000089, you'll get issues when composing to this:      -> 123045670.000000000089 (21 digits)      Make sure the numbers are close to each other as possible, with 1 zero (or 2) in between:      -> 1.230045670089 (13 digits by doing -> (123 * 10e-3) + (45.67 * 10e-7) + 0.000000000089) 🔹 This script contains examples of calculated values, % change, SMA, RMA and RSI.      These values need to be calculated from HTF close data at current TF (timeframe).      This gives challenges. For example the SMA / %change is not a problem (same values at 1h TF from Daily data).       RMA , RSI is not so easy though...      Daily values are rather similar on a 2-3h TF, but 1h TF and lower is quite different.      At the moment I haven't figured out why, if someone has an idea, don't hesitate to share.      The main goal of this publication is 'composite tickers ~ request.security()' though. 🔹 When a ticker value changes substantially (x10, x100), the multiply number needs to be adjusted accordingly. 🔶 SETTINGS SHOW SETS SET    •  Length : length of SMA, RMA and RSI    •  HTF : Higher TimeFrame (default Daily) TABLE    •  Size table :                         \ _ Self-explanatory    •  Include exchange name :  /    •  Sort : If exchange names are shown, the exchanges will be sorted first COLOURS    •  CH%    •  RSI    •  SMA (RMA) DEBUG Remember t46 , T16 ,... ? This can be used for debugging/checking ALWAYS DISABLE " sort " when doing so. Example: Set string -> T1 (tickers FIL, CAKE, SOL) (Numbers are slightly different due to time passing by between screen captures) Placing your tickers at the side panel makes it easy to compare with the printed label below the table (right side, 332201415014.45 ), together with the line T1 in the script: t1 = 'BINANCE:FILUSDT' , n1 = 10e10, r1 = 4, t2 = 'BINANCE:CAKEUSDT' , n2 = 10e5 , r2 = 3, t3 = 'BINANCE:SOLUSDT' , r3 = 2 // T1 FIL     :    3.322 CAKE:    1.415 SOL   : 14.56 Now it is easy to check whether the tickers are placed close enough to each other, with 1-2 zero's in between. If you want to check a specific ticker, use " Show Ticker" , see out initial example: Set string     -> T16 Show ticker -> 46 (in the code -> t46 = 'BINANCE:MTLUSDT') (Set at 0 to disable " check string " and NONE to disable " Set string ") -> Debug/check/set away! 😀 🔶 OTHER TECHNIQUES  • REGEX ( Regular expression ) and str.match() is used to delete the exchange name from the ticker, in other words, everything before ":" is deleted by following regex: exch(t) => incl_exch ? t : str.match(t, "(?<=:) +")  • To sort, array.sort_indices() is used (line 675 in the code), just as in my first "sort" publication Sort array alphabetically - educational aSort = arrT.copy() sort_Indices = array.sort_indices(id= aSort, order= order.ascending)  • Numbers and text colour will adjust automatically when switching between light/dark mode by using chart.fg_color / chart.bg_color 🔹 DISCLAIMER Please don't ask me for custom screeners, thank you.
Pine Script™ 인디케이터
fikira의
78
Multiple Moving Average ToolkitFeatures Overview: Multiple Moving Averages: The script allows you to plot up to five different Moving Averages (MAs) on your chart at the same time. You can choose the type of MA (EMA, SMA, HMA, WMA, DEMA, VWMA, VWAP) and the length of each one. Color Ribbon: You can turn the MAs into a color ribbon by selecting the "Turn into Color Ribbon?" option. This will make the area between the MAs colored and can help you identify trends more easily. MA Value Table: You can draw a table on your chart that displays the current values of each MA, whether the trend is bullish or bearish along with the length of the MAs. The current ATR value is also shown in the last cell of the table. You can choose the location of the table (Top Left, Top Right, Bottom Left, Bottom Right) and the transparency of the background color. Crosses: The script can detect when two MAs cross over each other (1st MA crosses 5th MA and vice versa), indicating a potential trend reversal. It will plot crosses on the chart at the point of the crossover and give an alert if the "Bullish Cross Detected" or "Bearish Cross Detected" condition is met. How to use: Once the script is added to your chart, you can customize the settings to fit your preferences. You can choose the type and length of each MA, whether to turn them into a color ribbon, whether to plot crosses, and whether to draw the MA Value Table. The MA Value Table can be moved to a different location on the chart by selecting the "Location of Table" option and choosing Top Left, Top Right, Bottom Left, or Bottom Right. Watch for MA crossovers and alerts to identify potential trend reversals. The script can help you identify bullish and bearish trends by color-coding the area between the MAs and displaying the current values of each MA in the table. Breakdown of the script: User Inputs The first section of the script defines several user inputs that allows you to customize the indicator. These include options for turning the MAs into a color ribbon, plotting crosses when there is a bullish or bearish cross of the MAs, drawing a table of the MA values, and setting the transparency of the ribbon. You can also select the location of the MA value table and customize the settings for each individual MA. Moving Average Calculation The script defines a function called "getMA" that calculates the moving average for a given type and length. The function uses a switch statement to determine which type of moving average to use, such as an exponential moving average (EMA), simple moving average (SMA), Hull moving average (HMA), weighted moving average (WMA), double exponential moving average (DEMA), volume-weighted moving average (VWMA), or volume-weighted average price (VWAP). The script then calls this function to calculate the values of up to five different MAs, depending on the user input. The ATR (average true range) is also calculated using the TA library. Color Filter and Cross Detection The script sets a color filter based on the relationship between the MAs. If the shorter-term MAs are above the longer-term MAs, the filter is set to green to indicate a bullish trend, and if the shorter-term MAs are below the longer-term MAs, the filter is set to red to indicate a bearish trend. You can adjust the transparency of the ribbon to make it more or less visible. The script also detects when there is a bullish or bearish cross of the MAs and can generate alerts to notify you. MA Plotting The script plots up to five MAs on the chart, depending on the user input. The MAs are plotted as lines with different colors and thicknesses, and you can choose to turn them into a color ribbon if desired. Cross Plotting The script plots crosses on the chart when there is a bullish or bearish cross of the MAs. The crosses are plotted as X shapes at the location of the cross and are color-coded to indicate the direction of the cross. MA Value Table Finally, the script draws a table of the MA values on the chart, displaying the values of each MA as well as the current trend and the ATR. You can customize the location of the table, and the table is colored to match the color filter of the MAs. Feel free to message me or comment on the post with any questions or issues! Much more to come! Thanks for reading, enjoy!
Pine Script™ 인디케이터
traderview2의
8
Parabolic Scalp Take Profit[ChartPrime]Indicators can be a great way to signal when the optimal time is for taking profits. However, many indicators are lagging in nature and will get market participants out of their trades at less than optimal price points. This take profit indicator uses the concept of slope and exponential gain to calculate when the optimal time is to take profits on your trades, thus making this a leading indicator. Usage: In essence the indicator will draw a parabolic line that starts from the market participants entry point and exponentially grows the slope of the line eventually intersecting with the price action. When price intersects with the parabolic line a take profit signal will appear in the form of an x. We have found that this take profit indicator is especially useful for scalp trades on lower timeframes. How To Use: Add the indicator to the chart. Click on the candle which the trade is on. Click on either the price which the trade will be at, or at the bottom of the candle in a long, or the top of a candle in a short. Select long or short. Open the settings of the indicator and adjust the aggressiveness to the desired value. Settings: - Start Time -- This is the bar in which your entry will be at, or occured at and the script will ask you to click on the bar with your mouse upon first adding the script. - Start Price -- This is the price in which the entry will be at, or was at and the script will ask you to click on the price with your mouse upon first adding the script. - Long/Short -- This is a setting which lets the script know if it is a long or a short trade, and the script will ask you to confirm this upon first adding it to the chart. - Aggressiveness -- This directly affects how aggressive the exponential curve is. A value of 101 is the lowest possible setting, indicating a very non-aggressive exponential buildup. A value of 200 is the highest and most aggressive setting, indicating a doubling effect per bar on the slope.
Pine Script™ 인디케이터
ChartPrime의
3
Bollinger Bands SignalsDescription: This indicator works well in trendy markets on long runs and in mean-reverting markets, at almost any timeframe. That said, higher timeframes are much preferred for their intrinsic ability to cut out noise. The example chart is in 3H TF. Be mindful, the script shows somewhat erratic jigsaw-like behaviour during consolidation periods when the price jumps up and down in indecision which way to go. Fortunately, there are scripts out there that detect such periods. You can choose between 4 Moving Averages, Vidya being the default. Period, Deviation and Bands Width parameters all of them affect the signal generation. For the Pine Script coder this script is pretty obvious. It uses a standard technical analysis indicator - Bollinger Bands - and appends it with a 'width' parameter and a signal generation procedure. The signal generation procedure is the heart of this script that keeps the script pumping signals. The BB width is used as a filter. You can use this procedure in your own scripts and it will continue generate signals according to your rules.
Pine Script™ 인디케이터
capissimo의
2
Percent Levels From Previous CloseThis indicator plots on the chart +/- 1% / 2% / 3% ranges based on the previous day's close levels. Disclaimer : Success in trading is all about following your trading strategy and indicators should fit into your own strategy, and not be traded purely on. This script is for informational and educational purposes only. Use of the script does not constitute professional and / or financial advice. You are solely responsible for evaluating the outcome of the script and the risks associated with using the script. In exchange for the use of the script, you agree not to hold monpotejulien TradingView user responsible for any possible claims for damages arising out of any decisions you make based on the use of the script.
Pine Script™ 인디케이터
Julien_Eche의
17
[CLX][#04] Progress BarsFully customizable progress bars. 🚥 Functions: - f_pbar() - 2 color, single argument version - f_bar_theme() - multi color, array version A detailed description will follow in the next few days. Feel free to contribute for an extended version. 😊 Still in development. We hope you enjoy it! 🎉 CRYPTOLINX - jango_blockchained 😊👍 Disclaimer: Trading success is all about following your trading strategy and the indicators should fit within your trading strategy, and not to be traded upon solely. The script is for informational and educational purposes only. Use of the script does not constitute professional and/or financial advice. You alone have the sole responsibility of evaluating the script output and risks associated with the use of the script. In exchange for using the script, you agree not to hold cryptolinx TradingView user liable for any possible claim for damages arising from any decision you make based on use of the script.
Pine Script™ 인디케이터
cryptolinx의
4
Machine Learning / Longs [Experimental]Hello Traders/Programmers, For long time I thought that if it's possible to make a script that has own memory and criterias in Pine. it would learn and find patterns as images according to given criterias. after we have arrays of strings, lines, labels I tried and made this experimental script. The script works only for Long positions. Now lets look at how it works: On each candle it creates an image of last 8 candles. before the image is created it finds highest/lowest levels of 8 candles, and creates a string with the lengths 64 (8 * 8). and for each square, it checks if it contains wick, green or red body, green or red body with wicks. see the following picture: Each square gets the value: 0: nothing in it 1: only wick in it 2: only red body in it 3. only green body in it 4: red body and wick in it 5: green body and wick in it And then it checks if price went up equal or higher than user-defined profit. if yes then it adds the image to the memory/array. and I call this part as Learning Part. what I mean by image is: if there is 1 or more element in the memory, it creates image for current 8 candles and checks the memory if there is a similar images. If the image has similarity higher than user-defined similarty level then if show the label "Matched" and similarity rate and the image in the memory. if it find any with the similarity rate is equal/greater than user-defined level then it stop searching more. As an example matched image: and then price increased and you got the profit :) Options: Period: if there is possible profit higher than user-defined minimum profit in that period, it checks the images from 2. to X. bars. Min Profit: you need to set the minimum expected profit accordingly. for example in 1m chart don't enter %10 as min profit :) Similarity Rate: as told above, you can set minimum similarity rate, higher similarity rate means better results but if you set higher rates, number of images will decrease. set it wisely :) Max Memory Size: you can set number of images (that gives the profit equal/higher than you set) to be saved that in memory Change Bar Color: optionally it can change bar colors if current image is found in the memory Current version of the script doesn't check if the price reach the minimum profit target, so no statistics. This is completely experimental work and I made it for fun. No one or no script can predict the future. and you should not try to predict the future. P.S. it starts searching on last bar, it doesn't check historical bars. if you want you should check it in replay mode :) if you get calculation time out error then hide/unhide the script. ;) Enjoy!
Pine Script™ 인디케이터
LonesomeTheBlue의
84
Bar Balance [LucF]Bar Balance extracts the number of up, down and neutral intrabars contained in each chart bar, revealing information on the strength of price movement. It can display stacked columns representing raw up/down/neutral intrabar counts, or an up/down balance line which can be calculated and visualized in many different ways. WARNING: This is an analysis tool that works on historical bars only. It does not show any realtime information, and thus cannot be used to issue alerts or for automated trading. When realtime bars elapse, the indicator will require a browser refresh, a change to its Inputs or to the chart's timeframe/symbol to recalculate and display information on those elapsed bars. Once a trader understands this, the indicator can be used advantageously to make discretionary trading decisions. Traders used to work with my  Delta Volume Columns Pro  will feel right at home in this indicator's Inputs . It has lots of options, allowing it to be used in many different ways. If you value the bar balance information this indicator mines, I hope you will find the time required to master the use of Bar Balance well worth the investment. █  OVERVIEW The indicator has two modes: Columns and Line . Columns • In Columns mode you can display stacked Up/Down/Neutral columns. • The "Up" section represents the count of intrabars where `close > open`, "Down" where `close < open` and "Neutral" where `close = open`. • The Up section always appears above the centerline, the Down section below. The Neutral section overlaps the centerline, split halfway above and below it.  The Up and Down sections start where the Neutral section ends, when there is one. • The Up and Down sections can be colored independently using 7 different methods. • The signal line plotted in Line mode can also be displayed in Columns mode. Line • Displays a single balance line using a zero centerline. • A variable number of independent methods can be used to calculate the line (6), determine its color (5), and color the fill (5).  You can thus evaluate the state of 3 different components with this single line. • A "Divergence Levels" feature will use the line to automatically draw expanding levels on divergence events. Features available in both modes • The color of all components can be selected from 15 base colors, with 16 gradient levels used for each base color in the indicator's gradients. • A zero line can show a 6-state aggregate value of the three main volume balance modes. • The background can be colored using any of 5 different methods. • Chart bars can be colored using 5 different methods. • Divergence and large neutral count ratio events can be shown in either Columns or Line mode, calculated in one of 4 different methods. • Markers on 6 different conditions can be displayed. █  CONCEPTS Intrabar inspection Intrabar inspection means the indicator looks at lower timeframe bars ( intrabars ) making up a given chart bar to gather its information. If your chart is on a 1-hour timeframe and the intrabar resolution determined by the indicator is 5 minutes, then 12 intrabars will be analyzed for each chart bar and the count of up/down/neutral intrabars among those will be tallied. Bar Balances and calculation methods The indicator uses a variety of methods to evaluate bar balance and to derive other calculations from them: 1. Balance on Bar : Uses the relative importance of instant Up and Down counts on the bar. 2. Balance Averages : Uses the difference between the EMAs of Up and Down counts. 3. Balance Momentum : Starts by calculating, separately for both Up and Down counts, the difference between the same EMAs used in Balance Averages and an SMA of double the period used for the EMAs. These differences are then aggregated and finally, a bounded momentum of that aggregate is calculated using RSI. 4. Markers Bias : It sums the bull/bear occurrences of the four previous markers over a user-defined period (the default is 14). 5. Combined Balances : This is the aggregate of the instant bull/bear bias of the three main bar balances. 6. Dual Up/Down Averages : This is a display mode showing the EMA calculated for each of the Up and Down counts. Interpretation of neutral intrabars What do neutral intrabars mean? When price does not change during a bar, it can be because there is simply no interest in the market, or because of a perfect balance between buyers and sellers. The latter being more improbable, Bar Balance assumes that neutral bars reveal a lack of interest, which entails uncertainty. That is the reason why the option is provided to interpret ratios of neutral intrabars greater than 50% as divergences. It is also the rationale behind the option to dampen signal lines on the inverse ratio of neutral intrabars, so that zero intrabars do not affect the signal, and progressively larger proportions of neutral intrabars will reduce the signal's amplitude, as the balance calcs using the up/down counts lose significance. The impact of the dampening will vary with markets. Weaker markets such as cryptos will often contain greater numbers of neutral intrabars, so dampening the Line in that sector will have a greater impact than in more liquid markets. █  FEATURES 1 — Columns • While the size of the Up/Down columns always represents their respective importance on the bar, their coloring mode is independent. The default setup uses a standard coloring mode where the Up/Down columns over/under the zero line are always in the bull/bear color with a higher intensity for the winning side. Six other coloring modes allow you to pack more information in the columns. When choosing to color the top columns using a bull/bear gradient on Balance Averages, for example, you will end up with bull/bear colored tops. In order for the color of the bottom columns to continue to show the instant bar balance, you can then choose the "Up/Down Ratio on Bar — Dual Solid Colors" coloring mode to make those bars the color of the winning side for that bar. • Line mode shows only the line, but Columns mode allows displaying the line along with it. If the scale of the line is different than that of the scale of the columns, the line will often appear flat. Traders may find even a flat line useful as its bull/bear colors will be easily distinguishable. 2 — Line • The default setup for Line mode uses a calculation on "Balance Momentum", with a fill on the longer-term "Balance Averages" and a line color based on the "Markers Bias". With the background set on "Line vs Divergence Levels" and the zero line on the hard-coded "Combined Bar Balances", you have access to five distinct sources of information at a glance, to which you can add divergences, divergences levels and chart bar coloring. This provides powerful potential in displaying bar balance information. • When no columns are displayed, Line mode can show the full scale of whichever line you choose to calculate because the columns' scale no longer interferes with the line's scale. • Note that when "Balance on Bar" is selected, the Neutral count is also displayed as a ratio of the balance line. This is the only instance where the Neutral count is displayed in Line mode. • The "Dual Up/Down Averages" is an exception as it displays two lines: one average for the Up counts and another for the Down counts. This mode will be most useful when Columns are also displayed, as it provides a reference for the top and bottom columns. 3 — Zero Line The zero line can be colored using two methods, both based on the Combined Balances, i.e., the aggregate of the instant bull/bear bias of the three main bar balances. • In "Six-state Dual Color Gradient" mode, a dot appears on every bar. Its color reflects the bull/bear state of the Combined Balances, and the dot's brightness reflects the tally of balance biases. • In "Dual Solid Colors (All Bull/All Bear Only)" a dot only appears when all three balances are either bullish or bearish. The resulting pattern is identical to that of Marker 1. 4 — Divergences • Divergences are displayed as a small circle at the top of the scale. Four different types of divergence events can be detected. Divergences occur whenever the bull/bear bias of the method used diverges with the bar's price direction. • An option allows you to include in divergence events instances where the count of neutral intrabars exceeds 50% of the total intrabar count. • The divergence levels are dynamic levels that automatically build from the line's values on divergence events. On consecutive divergences, the levels will expand, creating a channel. This implementation of the divergence levels corresponds to my view that divergences indicate anomalies, hesitations, points of uncertainty if you will. It excludes any association of a pre-determined bullish/bearish bias to divergences. Accordingly, the levels merely take note of divergence events and mark those points in time with levels. Traders then have a reference point from which they can evaluate further movement. The bull/bear/neutral colors used to plot the levels are also congruent with this view in that they are determined by price's position relative to the levels, which is how I think divergences can be put to the most effective use. 5 — Background • The background can show a bull/bear gradient on four different calculations. You can adjust its brightness to make its visual importance proportional to how you use it in your analysis. 6 — Chart bars • Chart bars can be colored using five different methods. • You have the option of emptying the body of bars where volume does not increase, as does my TLD indicator, the idea behind this being that movement on bars where volume does not increase is less relevant. 7 — Intrabar Resolution You can choose between three modes. Two of them are automatic and one is manual:   a) Fast, Longer history, Auto-Steps (~12 intrabars) : Optimized for speed and deeper history. Uses an average minimum of 12 intrabars.   b) More Precise, Shorter History Auto-Steps (~24 intrabars) : Uses finer intrabar resolution. It is slower and provides less history. Uses an average minimum of 24 intrabars.   c) Fixed : Uses the fixed resolution of your choice. Auto-Steps calculations vary for 24/7 and conventional markets in order to achieve the proper target of minimum intrabars. You can choose to view the intrabar resolution currently used to calculate delta volume. It is the default. The proper selection of the intrabar resolution is important. It must achieve maximal granularity to produce precise results while not unduly slowing down calculations, or worse, causing runtime errors. 8 — Markers Six markers are available: 1. Combined Balances Agreement : All three Bar Balances are either bullish or bearish. 2. Up or Down % Agrees With Bar : An up marker will appear when the percentage of up intrabars in an up chart bar is greater than the specified percentage. Conditions mirror to down bars. 3. Divergence confirmations By Price : One of the four types of balance calculations can be used to detect divergences with price. Confirmations occur when the bar following the divergence confirms the balance bias. Note that the divergence events used here do not include neutral intrabar events. 4. Balance Transitions : Bull/bear transitions of the selected balance. 5. Markers Bias Transitions : Bull/bear transitions of the Markers Bias. 6. Divergence Confirmations By Line : Marks points where the line first breaches a divergence level. Markers appear when the condition is detected, without delay. Since nothing is plotted in realtime, markers do not appear on the realtime bar. 9 — Settings • Two modes can be selected to dampen the line on the ratio of neutral intrabars. • A distinct weight can be attributed to the count of the latter half of intrabars, on the assumption that later intrabars may be more important in determining the outcome of chart bars. • Allows control over the periods of the different moving averages used in calculations. • The default periods used for the various calculations define the following hierarchy from slow to fast:   Balance Averages: 50,   Balance Momentum: 20,   Dual Up/Down Averages: 20,   Marker Bias: 10. █  LIMITATIONS • This script uses a special characteristic of the `security()` function allowing the inspection of intrabars—which is not officially supported by TradingView. • The method used does not work on the realtime bar—only on historical bars. • The indicator only works on some chart resolutions: 3, 5, 10, 15 and 30 minutes, 1, 2, 4, 6, and 12 hours, 1 day, 1 week and 1 month. The script’s code can be modified to run on other resolutions, but chart resolutions must be divisible by the lower resolution used for intrabars and the stepping mechanism could require adaptation. • When using the "Line vs Divergence Levels — Dual Color Gradient" color mode to fill the line, background or chart bars, keep in mind that a line calculation mode must be defined for it to work, as it determines gradients on the movement of the line relative to divergence levels. If the line is hidden, it will not work. • When the difference between the chart’s resolution and the intrabar resolution is too great, runtime errors will occur. The Auto-Steps selection mechanisms should avoid this. • Alerts do not work reliably when `security()` is used at intrabar resolutions. Accordingly, no alerts are configured in the indicator. • The color model used in the indicator provides for fancy visuals that come at a price; when you change values in Inputs , it can take 20 seconds for the changes to materialize. Luckily, once your color setup is complete, the color model does not have a large performance impact, as in normal operation the `security()` calls will become the most important factor in determining response time. Also, once in a while a runtime error will occur when you change inputs. Just making another change will usually bring the indicator back up. █  RAMBLINGS Is this thing useful? I'll let you decide. Bar Balance acts somewhat like an X-Ray on bars. The intrabars it analyzes are no secret; one can simply change the chart's resolution to see the same intrabars the indicator uses. What the indicator brings to traders is the precise count of up/down/neutral intrabars and, more importantly, the calculations it derives from them to present the information in a way that can make it easier to use in trading decisions. How reliable is Bar Balance information? By the same token that an up bar does not guarantee that more up bars will follow, future price movements cannot be inferred from the mere count of up/down/neutral intrabars. Price movement during any chart bar for which, let's say, 12 intrabars are analyzed, could be due to only one of those intrabars. One can thus easily see how only relying on bar balance information could be very misleading. The rationale behind Bar Balance is that when the information mined for multiple chart bars is aggregated, it can provide insight into the history behind chart bars, and thus some bias as to the strength of movements. An up chart bar where 11/12 intrabars are also up is assumed to be stronger than the same up bar where only 2/12 intrabars are up. This logic is not bulletproof, and sometimes Bar Balance will stray. Also, keep in mind that balance lines do not represent price momentum as RSI would. Bar Balance calculations have no idea where price is. Their perspective, like that of any historian, is very limited, constrained that it is to the narrow universe of up/down/neutral intrabar counts. You will thus see instances where price is moving up while Balance Momentum, for example, is moving down. When Bar Balance performs as intended, this indicates that the rally is weakening, which does necessarily imply that price will reverse. Occasionally, price will merrily continue to advance on weakening strength. Divergences Most of the divergence detection methods used here rely on a difference between the bias of a calculation involving a multi-bar average and a given bar's price direction. When using "Bar Balance on Bar" however, only the bar's balance and price movement are used. This is the default mode. As usual, divergences are points of interest because they reveal imbalances, which may or may not become turning points. I do not share the overwhelming enthusiasm traders have for the purported ability of bullish/bearish divergences to indicate imminent reversals. Superfluity In "The Bed of Procrustes", Nassim Nicholas Taleb writes: To bankrupt a fool, give him information . Bar Balance can display lots of information. While learning to use a new indicator inevitably requires an adaptation period where we put it through its paces and try out all its options, once you have become used to Bar Balance and decide to adopt it, rigorously eliminate the components you don't use and configure the remaining ones so their visual prominence reflects their relative importance in your analysis. I tried to provide flexible options for traders to control this indicator's visuals for that exact reason—not for window dressing. █  NOTES For traders • To avoid misleading traders who don't read script descriptions, the indicator shows nothing in the realtime bar. • The Data Window shows key values for the indicator. • All gradients used in this indicator determine their brightness intensities using advances/declines in the signal—not their relative position in a fixed scale. • Note that because of the way gradients are optimized internally, changing their brightness will sometimes require bringing down the value a few steps before you see an impact. • Because this indicator does not use volume, it will work on all markets. For coders • For those interested in gradients, this script uses an advanced version of the Advance/Decline gradient function from the PineCoders Color Gradient (16 colors) Framework . It allows more precise control over the range, steps and min/max values of the gradients. • I use the PineCoders Coding Conventions for Pine to write my scripts. • I used functions modified from the PineCoders MTF Selection Framework for the selection of timeframes. █  THANKS TO: — alexgrover who helped me think through the dampening method used to attenuate signal lines on high ratios of neutral intrabars. — A guy called Kuan who commented on a Backtest Rookies presentation of their Volume Profile indicator . The technique I use to inspect intrabars is derived from Kuan's code. — theheirophant , my partner in the exploration of the sometimes weird abysses of `security()`’s behavior at intrabar resolutions. — midtownsk8rguy , my brilliant companion in mining the depths of Pine graphics. He is also the co-author of the PineCoders Color Gradient Frameworks .
Pine Script™ 인디케이터
LucF의
29
Backtesting & Trading Engine [PineCoders]The PineCoders Backtesting and Trading Engine is a sophisticated framework with hybrid code that can run as a study to generate alerts for automated or discretionary trading while simultaneously providing backtest results. It can also easily be converted to a TradingView strategy in order to run TV backtesting. The Engine comes with many built-in strats for entries, filters, stops and exits, but you can also add you own. If, like any self-respecting strategy modeler should, you spend a reasonable amount of time constantly researching new strategies and tinkering, our hope is that the Engine will become your inseparable go-to tool to test the validity of your creations, as once your tests are conclusive, you will be able to run this code as a study to generate the alerts required to put it in real-world use, whether for discretionary trading or to interface with an execution bot/app. You may also find the backtesting results the Engine produces in study mode enough for your needs and spend most of your time there, only occasionally converting to strategy mode in order to backtest using TV backtesting. As you will quickly grasp when you bring up this script’s Settings, this is a complex tool. While you will be able to see results very quickly by just putting it on a chart and using its built-in strategies, in order to reap the full benefits of the PineCoders Engine, you will need to invest the time required to understand the subtleties involved in putting all its potential into play. Disclaimer: use the Engine at your own risk. Before we delve in more detail, here’s a bird’s eye view of the Engine’s features: More than 40 built-in strategies, Customizable components, Coupling with your own external indicator, Simple conversion from Study to Strategy modes, Post-Exit analysis to search for alternate trade outcomes, Use of the Data Window to show detailed bar by bar trade information and global statistics, including some not provided by TV backtesting, Plotting of reminders and generation of alerts on in-trade events. By combining your own strats to the built-in strats supplied with the Engine, and then tuning the numerous options and parameters in the Inputs dialog box, you will be able to play what-if scenarios from an infinite number of permutations. USE CASES You have written an indicator that provides an entry strat but it’s missing other components like a filter and a stop strategy. You add a plot in your indicator that respects the Engine’s External Signal Protocol, connect it to the Engine by simply selecting your indicator’s plot name in the Engine’s Settings/Inputs and then run tests on different combinations of entry stops, in-trade stops and profit taking strats to find out which one produces the best results with your entry strat. You are building a complex strategy that you will want to run as an indicator generating alerts to be sent to a third-party execution bot. You insert your code in the Engine’s modules and leverage its trade management code to quickly move your strategy into production. You have many different filters and want to explore results using them separately or in combination. Integrate the filter code in the Engine and run through different permutations or hook up your filtering through the external input and control your filter combos from your indicator. You are tweaking the parameters of your entry, filter or stop strat. You integrate it in the Engine and evaluate its performance using the Engine’s statistics. You always wondered what results a random entry strat would yield on your markets. You use the Engine’s built-in random entry strat and test it using different combinations of filters, stop and exit strats. You want to evaluate the impact of fees and slippage on your strategy. You use the Engine’s inputs to play with different values and get immediate feedback in the detailed numbers provided in the Data Window. You just want to inspect the individual trades your strategy generates. You include it in the Engine and then inspect trades visually on your charts, looking at the numbers in the Data Window as you move your cursor around. You have never written a production-grade strategy and you want to learn how. Inspect the code in the Engine; you will find essential components typical of what is being used in actual trading systems. You have run your system for a while and have compiled actual slippage information and your broker/exchange has updated his fees schedule. You enter the information in the Engine and run it on your markets to see the impact this has on your results. FEATURES Before going into the detail of the Inputs and the Data Window numbers, here’s a more detailed overview of the Engine’s features. Built-in strats The engine comes with more than 40 pre-coded strategies for the following standard system components: Entries, Filters, Entry stops, 2 stage in-trade stops with kick-in rules, Pyramiding rules, Hard exits. While some of the filter and stop strats provided may be useful in production-quality systems, you will not devise crazy profit-generating systems using only the entry strats supplied; that part is still up to you, as will be finding the elusive combination of components that makes winning systems. The Engine will, however, provide you with a solid foundation where all the trade management nitty-gritty is handled for you. By binding your custom strats to the Engine, you will be able to build reliable systems of the best quality currently allowed on the TV platform. On-chart trade information As you move over the bars in a trade, you will see trade numbers in the Data Window change at each bar. The engine calculates the P&L at every bar, including slippage and fees that would be incurred were the trade exited at that bar’s close. If the trade includes pyramided entries, those will be taken into account as well, although for those, final fees and slippage are only calculated at the trade’s exit. You can also see on-chart markers for the entry level, stop positions, in-trade special events and entries/exits (you will want to disable these when using the Engine in strategy mode to see TV backtesting results). Customization You can couple your own strats to the Engine in two ways: 1. By inserting your own code in the Engine’s different modules. The modular design should enable you to do so with minimal effort by following the instructions in the code. 2. By linking an external indicator to the engine. After making the proper selections in the engine’s Settings and providing values respecting the engine’s protocol, your external indicator can, when the Engine is used in Indicator mode only: Tell the engine when to enter long or short trades, but let the engine’s in-trade stop and exit strats manage the exits, Signal both entries and exits, Provide an entry stop along with your entry signal, Filter other entry signals generated by any of the engine’s entry strats. Conversion from strategy to study TradingView strategies are required to backtest using the TradingView backtesting feature, but if you want to generate alerts with your script, whether for automated trading or just to trigger alerts that you will use in discretionary trading, your code has to run as a study since, for the time being, strategies can’t generate alerts. From hereon we will use indicator as a synonym for study. Unless you want to maintain two code bases, you will need hybrid code that easily flips between strategy and indicator modes, and your code will need to restrict its use of strategy() calls and their arguments if it’s going to be able to run both as an indicator and a strategy using the same trade logic. That’s one of the benefits of using this Engine. Once you will have entered your own strats in the Engine, it will be a matter of commenting/uncommenting only four lines of code to flip between indicator and strategy modes in a matter of seconds. Additionally, even when running in Indicator mode, the Engine will still provide you with precious numbers on your individual trades and global results, some of which are not available with normal TradingView backtesting. Post-Exit Analysis for alternate outcomes (PEA) While typical backtesting shows results of trade outcomes, PEA focuses on what could have happened after the exit. The intention is to help traders get an idea of the opportunity/risk in the bars following the trade in order to evaluate if their exit strategies are too aggressive or conservative. After a trade is exited, the Engine’s PEA module continues analyzing outcomes for a user-defined quantity of bars. It identifies the maximum opportunity and risk available in that space, and calculates the drawdown required to reach the highest opportunity level post-exit, while recording the number of bars to that point. Typically, if you can’t find opportunity greater than 1X past your trade using a few different reasonable lengths of PEA, your strategy is doing pretty good at capturing opportunity. Remember that 100% of opportunity is never capturable. If, however, PEA was finding post-trade maximum opportunity of 3 or 4X with average drawdowns of 0.3 to those areas, this could be a clue revealing your system is exiting trades prematurely. To analyze PEA numbers, you can uncomment complete sets of plots in the Plot module to reveal detailed global and individual PEA numbers. Statistics The Engine provides stats on your trades that TV backtesting does not provide, such as: Average Profitability Per Trade (APPT), aka statistical expectancy, a crucial value. APPT per bar, Average stop size, Traded volume . It also shows you on a trade-by-trade basis, on-going individual trade results and data. In-trade events In-trade events can plot reminders and trigger alerts when they occur. The built-in events are: Price approaching stop, Possible tops/bottoms, Large stop movement (for discretionary trading where stop is moved manually), Large price movements. Slippage and Fees Even when running in indicator mode, the Engine allows for slippage and fees to be included in the logic and test results. Alerts The alert creation mechanism allows you to configure alerts on any combination of the normal or pyramided entries, exits and in-trade events. Backtesting results A few words on the numbers calculated in the Engine. Priority is given to numbers not shown in TV backtesting, as you can readily convert the script to a strategy if you need them. We have chosen to focus on numbers expressing results relative to X (the trade’s risk) rather than in absolute currency numbers or in other more conventional but less useful ways. For example, most of the individual trade results are not shown in percentages, as this unit of measure is often less meaningful than those expressed in units of risk (X). A trade that closes with a +25% result, for example, is a poor outcome if it was entered with a -50% stop. Expressed in X, this trade’s P&L becomes 0.5, which provides much better insight into the trade’s outcome. A trade that closes with a P&L of +2X has earned twice the risk incurred upon entry, which would represent a pre-trade risk:reward ratio of 2. The way to go about it when you think in X’s and that you adopt the sound risk management policy to risk a fixed percentage of your account on each trade is to equate a currency value to a unit of X. E.g. your account is 10K USD and you decide you will risk a maximum of 1% of it on each trade. That means your unit of X for each trade is worth 100 USD. If your APPT is 2X, this means every time you risk 100 USD in a trade, you can expect to make, on average, 200 USD. By presenting results this way, we hope that the Engine’s statistics will appeal to those cognisant of sound risk management strategies, while gently leading traders who aren’t, towards them. We trade to turn in tangible profits of course, so at some point currency must come into play. Accordingly, some values such as equity, P&L, slippage and fees are expressed in currency. Many of the usual numbers shown in TV backtests are nonetheless available, but they have been commented out in the Engine’s Plot module. Position sizing and risk management All good system designers understand that optimal risk management is at the very heart of all winning strategies. The risk in a trade is defined by the fraction of current equity represented by the amplitude of the stop, so in order to manage risk optimally on each trade, position size should adjust to the stop’s amplitude. Systems that enter trades with a fixed stop amplitude can get away with calculating position size as a fixed percentage of current equity. In the context of a test run where equity varies, what represents a fixed amount of risk translates into different currency values. Dynamically adjusting position size throughout a system’s life is optimal in many ways. First, as position sizing will vary with current equity, it reproduces a behavioral pattern common to experienced traders, who will dial down risk when confronted to poor performance and increase it when performance improves. Second, limiting risk confers more predictability to statistical test results. Third, position sizing isn’t just about managing risk, it’s also about maximizing opportunity. By using the maximum leverage (no reference to trading on margin here) into the trade that your risk management strategy allows, a dynamic position size allows you to capture maximal opportunity. To calculate position sizes using the fixed risk method, we use the following formula: Position = Account * MaxRisk% / Stop% [, which calculates a position size taking into account the trade’s entry stop so that if the trade is stopped out, 100 USD will be lost. For someone who manages risk this way, common instructions to invest a certain percentage of your account in a position are simply worthless, as they do not take into account the risk incurred in the trade. The Engine lets you select either the fixed risk or fixed percentage of equity position sizing methods. The closest thing to dynamic position sizing that can currently be done with alerts is to use a bot that allows syntax to specify position size as a percentage of equity which, while being dynamic in the sense that it will adapt to current equity when the trade is entered, does not allow us to modulate position size using the stop’s amplitude. Changes to alerts are on the way which should solve this problem. In order for you to simulate performance with the constraint of fixed position sizing, the Engine also offers a third, less preferable option, where position size is defined as a fixed percentage of initial capital so that it is constant throughout the test and will thus represent a varying proportion of current equity. Let’s recap. The three position sizing methods the Engine offers are: 1. By specifying the maximum percentage of risk to incur on your remaining equity, so the Engine will dynamically adjust position size for each trade so that, combining the stop’s amplitude with position size will yield a fixed percentage of risk incurred on current equity, 2. By specifying a fixed percentage of remaining equity. Note that unless your system has a fixed stop at entry, this method will not provide maximal risk control, as risk will vary with the amplitude of the stop for every trade. This method, as the first, does however have the advantage of automatically adjusting position size to equity. It is the Engine’s default method because it has an equivalent in TV backtesting, so when flipping between indicator and strategy mode, test results will more or less correspond. 3. By specifying a fixed percentage of the Initial Capital. While this is the least preferable method, it nonetheless reflects the reality confronted by most system designers on TradingView today. In this case, risk varies both because the fixed position size in initial capital currency represents a varying percentage of remaining equity, and because the trade’s stop amplitude may vary, adding another variability vector to risk. Note that the Engine cannot display equity results for strategies entering trades for a fixed amount of shares/contracts at a variable price. SETTINGS/INPUTS Because the initial text first published with a script cannot be edited later and because there are just too many options, the Engine’s Inputs will not be covered in minute detail, as they will most certainly evolve. We will go over them with broad strokes; you should be able to figure the rest out. If you have questions, just ask them here or in the PineCoders Telegram group. Display The display header’s checkbox does nothing. For the moment, only one exit strategy uses a take profit level, so only that one will show information when checking “Show Take Profit Level”. Entries You can activate two simultaneous entry strats, each selected from the same set of strats contained in the Engine. If you select two and they fire simultaneously, the main strat’s signal will be used. The random strat in each list uses a different seed, so you will get different results from each. The “Filter transitions” and “Filter states” strats delegate signal generation to the selected filter(s). “Filter transitions” signals will only fire when the filter transitions into bull/bear state, so after a trade is stopped out, the next entry may take some time to trigger if the filter’s state does not change quickly. When you choose “Filter states”, then a new trade will be entered immediately after an exit in the direction the filter allows. If you select “External Indicator”, your indicator will need to generate a +2/-2 (or a positive/negative stop value) to enter a long/short position, providing the selected filters allow for it. If you wish to use the Engine’s capacity to also derive the entry stop level from your indicator’s signal, then you must explicitly choose this option in the Entry Stops section. Filters You can activate as many filters as you wish; they are additive. The “Maximum stop allowed on entry” is an important component of proper risk management. If your system has an average 3% stop size and you need to trade using fixed position sizes because of alert/execution bot limitations, you must use this filter because if your system was to enter a trade with a 15% stop, that trade would incur 5 times the normal risk, and its result would account for an abnormally high proportion in your system’s performance. Remember that any filter can also be used as an entry signal, either when it changes states, or whenever no trade is active and the filter is in a bull or bear mode. Entry Stops An entry stop must be selected in the Engine, as it requires a stop level before the in-trade stop is calculated. Until the selected in-trade stop strat generates a stop that comes closer to price than the entry stop (or respects another one of the in-trade stops kick in strats), the entry stop level is used. It is here that you must select “External Indicator” if your indicator supplies a +price/-price value to be used as the entry stop. A +price is expected for a long entry and a -price value will enter a short with a stop at price. Note that the price is the absolute price, not an offset to the current price level. In-Trade Stops The Engine comes with many built-in in-trade stop strats. Note that some of them share the “Length” and “Multiple” field, so when you swap between them, be sure that the length and multiple in use correspond to what you want for that stop strat. Suggested defaults appear with the name of each strat in the dropdown. In addition to the strat you wish to use, you must also determine when it kicks in to replace the initial entry’s stop, which is determined using different strats. For strats where you can define a positive or negative multiple of X, percentage or fixed value for a kick-in strat, a positive value is above the trade’s entry fill and a negative one below. A value of zero represents breakeven. Pyramiding What you specify in this section are the rules that allow pyramiding to happen. By themselves, these rules will not generate pyramiding entries. For those to happen, entry signals must be issued by one of the active entry strats, and conform to the pyramiding rules which act as a filter for them. The “Filter must allow entry” selection must be chosen if you want the usual system’s filters to act as additional filtering criteria for your pyramided entries. Hard Exits You can choose from a variety of hard exit strats. Hard exits are exit strategies which signal trade exits on specific events, as opposed to price breaching a stop level in In-Trade Stops strategies. They are self-explanatory. The last one labelled When Take Profit Level (multiple of X) is reached is the only one that uses a level, but contrary to stops, it is above price and while it is relative because it is expressed as a multiple of X, it does not move during the trade. This is the level called Take Profit that is show when the “Show Take Profit Level” checkbox is checked in the Display section. While stops focus on managing risk, hard exit strategies try to put the emphasis on capturing opportunity. Slippage You can define it as a percentage or a fixed value, with different settings for entries and exits. The entry and exit markers on the chart show the impact of slippage on the entry price (the fill). Fees Fees, whether expressed as a percentage of position size in and out of the trade or as a fixed value per in and out, are in the same units of currency as the capital defined in the Position Sizing section. Fees being deducted from your Capital, they do not have an impact on the chart marker positions. In-Trade Events These events will only trigger during trades. They can be helpful to act as reminders for traders using the Engine as assistance to discretionary trading. Post-Exit Analysis It is normally on. Some of its results will show in the Global Numbers section of the Data Window. Only a few of the statistics generated are shown; many more are available, but commented out in the Plot module. Date Range Filtering Note that you don’t have to change the dates to enable/diable filtering. When you are done with a specific date range, just uncheck “Date Range Filtering” to disable date filtering. Alert Triggers Each selection corresponds to one condition. Conditions can be combined into a single alert as you please. Just be sure you have selected the ones you want to trigger the alert before you create the alert. For example, if you trade in both directions and you want a single alert to trigger on both types of exits, you must select both “Long Exit” and “Short Exit” before creating your alert. Once the alert is triggered, these settings no longer have relevance as they have been saved with the alert. When viewing charts where an alert has just triggered, if your alert triggers on more than one condition, you will need the appropriate markers active on your chart to figure out which condition triggered the alert, since plotting of markers is independent of alert management. Position sizing You have 3 options to determine position size: 1. Proportional to Stop -> Variable, with a cap on size. 2. Percentage of equity -> Variable. 3. Percentage of Initial Capital -> Fixed. External Indicator This is where you connect your indicator’s plot that will generate the signals the Engine will act upon. Remember this only works in Indicator mode. DATA WINDOW INFORMATION The top part of the window contains global numbers while the individual trade information appears in the bottom part. The different types of units used to express values are: curr: denotes the currency used in the Position Sizing section of Inputs for the Initial Capital value. quote: denotes quote currency, i.e. the value the instrument is expressed in, or the right side of the market pair (USD in EURUSD ). X: the stop’s amplitude, itself expressed in quote currency, which we use to express a trade’s P&L, so that a trade with P&L=2X has made twice the stop’s amplitude in profit. This is sometimes referred to as R, since it represents one unit of risk. It is also the unit of measure used in the APPT, which denotes expected reward per unit of risk. X%: is also the stop’s amplitude, but expressed as a percentage of the Entry Fill. The numbers appearing in the Data Window are all prefixed: “ALL:” the number is the average for all first entries and pyramided entries. ”1ST:” the number is for first entries only. ”PYR:” the number is for pyramided entries only. ”PEA:” the number is for Post-Exit Analyses Global Numbers Numbers in this section represent the results of all trades up to the cursor on the chart. Average Profitability Per Trade (X): This value is the most important gauge of your strat’s worthiness. It represents the returns that can be expected from your strat for each unit of risk incurred. E.g.: your APPT is 2.0, thus for every unit of currency you invest in a trade, you can on average expect to obtain 2 after the trade. APPT is also referred to as “statistical expectancy”. If it is negative, your strategy is losing, even if your win rate is very good (it means your winning trades aren’t winning enough, or your losing trades lose too much, or both). Its counterpart in currency is also shown, as is the APPT/bar, which can be a useful gauge in deciding between rivalling systems. Profit Factor: Gross of winning trades/Gross of losing trades. Strategy is profitable when >1. Not as useful as the APPT because it doesn’t take into account the win rate and the average win/loss per trade. It is calculated from the total winning/losing results of this particular backtest and has less predictive value than the APPT. A good profit factor together with a poor APPT means you just found a chart where your system outperformed. Relying too much on the profit factor is a bit like a poker player who would think going all in with two’s against aces is optimal because he just won a hand that way. Win Rate: Percentage of winning trades out of all trades. Taken alone, it doesn’t have much to do with strategy profitability. You can have a win rate of 99% but if that one trade in 100 ruins you because of poor risk management, 99% doesn’t look so good anymore. This number speaks more of the system’s profile than its worthiness. Still, it can be useful to gauge if the system fits your personality. It can also be useful to traders intending to sell their systems, as low win rate systems are more difficult to sell and require more handholding of worried customers. Equity (curr): This the sum of initial capital and the P&L of your system’s trades, including fees and slippage. Return on Capital is the equivalent of TV’s Net Profit figure, i.e. the variation on your initial capital. Maximum drawdown is the maximal drawdown from the highest equity point until the drop . There is also a close to close (meaning it doesn’t take into account in-trade variations) maximum drawdown value commented out in the code. The next values are self-explanatory, until: PYR: Avg Profitability Per Entry (X): this is the APPT for all pyramided entries. PEA: Avg Max Opp . Available (X): the average maximal opportunity found in the Post-Exit Analyses. PEA: Avg Drawdown to Max Opp . (X): this represents the maximum drawdown (incurred from the close at the beginning of the PEA analysis) required to reach the maximal opportunity point. Trade Information Numbers in this section concern only the current trade under the cursor. Most of them are self-explanatory. Use the description’s prefix to determine what the values applies to. PYR: Avg Profitability Per Entry (X): While this value includes the impact of all current pyramided entries (and only those) and updates when you move your cursor around, P&L only reflects fees at the trade’s last bar. PEA: Max Opp . Available (X): It’s the most profitable close reached post-trade, measured from the trade’s Exit Fill, expressed in the X value of the trade the PEA follows. PEA: Drawdown to Max Opp . (X): This is the maximum drawdown from the trade’s Exit Fill that needs to be sustained in order to reach the maximum opportunity point, also expressed in X. Note that PEA numbers do not include slippage and fees. EXTERNAL SIGNAL PROTOCOL Only one external indicator can be connected to a script; in order to leverage its use to the fullest, the engine provides options to use it as either an entry signal, an entry/exit signal or a filter. When used as an entry signal, you can also use the signal to provide the entry’s stop. Here’s how this works: For filter state: supply +1 for bull (long entries allowed), -1 for bear (short entries allowed). For entry signals: supply +2 for long, -2 for short. For exit signals: supply +3 for exit from long, -3 for exit from short. To send an entry stop level with an entry signal: Send positive stop level for long entry (e.g. 103.33 to enter a long with a stop at 103.33), negative stop level for short entry (e.g. -103.33 to enter a short with a stop at 103.33). If you use this feature, your indicator will have to check for exact stop levels of 1.0, 2.0 or 3.0 and their negative counterparts, and fudge them with a tick in order to avoid confusion with other signals in the protocol. Remember that mere generation of the values by your indicator will have no effect until you explicitly allow their use in the appropriate sections of the Engine’s Settings/Inputs. An example of a script issuing a signal for the Engine is published by PineCoders. RECOMMENDATIONS TO ASPIRING SYSTEM DESIGNERS Stick to higher timeframes. On progressively lower timeframes, margins decrease and fees and slippage take a proportionally larger portion of profits, to the point where they can very easily turn a profitable strategy into a losing one. Additionally, your margin for error shrinks as the equilibrium of your system’s profitability becomes more fragile with the tight numbers involved in the shorter time frames. Avoid <1H time frames. Know and calculate fees and slippage. To avoid market shock, backtest using conservative fees and slippage parameters. Systems rarely show unexpectedly good returns when they are confronted to the markets, so put all chances on your side by being outrageously conservative—or a the very least, realistic. Test results that do not include fees and slippage are worthless. Slippage is there for a reason, and that’s because our interventions in the market change the market. It is easier to find alpha in illiquid markets such as cryptos because not many large players participate in them. If your backtesting results are based on moving large positions and you don’t also add the inevitable slippage that will occur when you enter/exit thin markets, your backtesting will produce unrealistic results. Even if you do include large slippage in your settings, the Engine can only do so much as it will not let slippage push fills past the high or low of the entry bar, but the gap may be much larger in illiquid markets. Never test and optimize your system on the same dataset , as that is the perfect recipe for overfitting or data dredging, which is trying to find one precise set of rules/parameters that works only on one dataset. These setups are the most fragile and often get destroyed when they meet the real world. Try to find datasets yielding more than 100 trades. Less than that and results are not as reliable. Consider all backtesting results with suspicion. If you never entertained sceptic tendencies, now is the time to begin. If your backtest results look really good, assume they are flawed, either because of your methodology, the data you’re using or the software doing the testing. Always assume the worse and learn proper backtesting techniques such as monte carlo simulations and walk forward analysis to avoid the traps and biases that unchecked greed will set for you. If you are not familiar with concepts such as survivor bias, lookahead bias and confirmation bias, learn about them. Stick to simple bars or candles when designing systems. Other types of bars often do not yield reliable results, whether by design (Heikin Ashi) or because of the way they are implemented on TV (Renko bars). Know that you don’t know and use that knowledge to learn more about systems and how to properly test them, about your biases, and about yourself. Manage risk first , then capture opportunity. Respect the inherent uncertainty of the future. Cleanse yourself of the sad arrogance and unchecked greed common to newcomers to trading. Strive for rationality. Respect the fact that while backtest results may look promising, there is no guarantee they will repeat in the future (there is actually a high probability they won’t!), because the future is fundamentally unknowable. If you develop a system that looks promising, don’t oversell it to others whose greed may lead them to entertain unreasonable expectations. Have a plan. Understand what king of trading system you are trying to build. Have a clear picture or where entries, exits and other important levels will be in the sort of trade you are trying to create with your system. This stated direction will help you discard more efficiently many of the inevitably useless ideas that will pop up during system design. Be wary of complexity. Experienced systems engineers understand how rapidly complexity builds when you assemble components together—however simple each one may be. The more complex your system, the more difficult it will be to manage. Play! . Allow yourself time to play around when you design your systems. While much comes about from working with a purpose, great ideas sometimes come out of just trying things with no set goal, when you are stuck and don’t know how to move ahead. Have fun! @LucF NOTES While the engine’s code can supply multiple consecutive entries of longs or shorts in order to scale positions (pyramid), all exits currently assume the execution bot will exit the totality of the position. No partial exits are currently possible with the Engine. Because the Engine is literally crippled by the limitations on the number of plots a script can output on TV; it can only show a fraction of all the information it calculates in the Data Window. You will find in the Plot Module vast amounts of commented out lines that you can activate if you also disable an equivalent number of other plots. This may be useful to explore certain characteristics of your system in more detail. When backtesting using the TV backtesting feature, you will need to provide the strategy parameters you wish to use through either Settings/Properties or by changing the default values in the code’s header. These values are defined in variables and used not only in the strategy() statement, but also as defaults in the Engine’s relevant Inputs. If you want to test using pyramiding, then both the strategy’s Setting/Properties and the Engine’s Settings/Inputs need to allow pyramiding. If you find any bugs in the Engine, please let us know. THANKS To @glaz for allowing the use of his unpublished MA Squize in the filters. To @everget for his Chandelier stop code, which is also used as a filter in the Engine. To @RicardoSantos for his pseudo-random generator, and because it’s from him that I first read in the Pine chat about the idea of using an external indicator as input into another. In the PineCoders group, @theheirophant then mentioned the idea of using it as a buy/sell signal and @simpelyfe showed a piece of code implementing the idea. That’s the tortuous story behind the use of the external indicator in the Engine. To @admin for the Volatility stop’s original code and for the donchian function lifted from Ichimoku . To @BobHoward21 for the v3 version of Volatility Stop . To @scarf and @midtownsk8rguy for the color tuning. To many other scripters who provided encouragement and suggestions for improvement during the long process of writing and testing this piece of code. To J. Welles Wilder Jr. for ATR, used extensively throughout the Engine. To TradingView for graciously making an account available to PineCoders. And finally, to all fellow PineCoders for the constant intellectual stimulation; it is a privilege to share ideas with you all. The Engine is for all TradingView PineCoders, of course—but especially for you. Look first. Then leap.
Pine Script™ 인디케이터
PineCoders의
129
SW monthly Gann Days**Script Description:** The script you are looking at is based on the work of W.D. Gann, a famous trader and market analyst in the early 20th century, known for his use of geometry, astrology, and numerology in market analysis. Gann believed that certain days in the market had significant importance, and he observed that markets often exhibited significant price moves around specific dates. These dates were typically associated with cyclical patterns in price movements, and Gann referred to these as "Gann Days." In this script, we have focused on highlighting certain days of the month that Gann believed to have an influence on market behavior. The specific days in question are the **6th to 7th**, **9th to 10th**, **14th to 15th**, **19th to 20th**, **23rd to 24th**, and **29th to 31st** of each month. These ranges are based on Gann’s theory that there are recurring time cycles in the market that cause turning points or critical price movements to occur around certain days of the month. ### **Why Gann Used These Days:** 1. **Mathematical and Astrological Cycles:** Gann believed that markets were influenced by natural cycles, and that certain dates (or combinations of dates) played a critical role in the price movements. These specific days are part of his broader theory of "time cycles" where the market would often change direction, reverse, or exhibit significant volatility on particular days. Gann's research was based on both mathematical principles and astrological observations, leading him to assign importance to these days. 2. **Gann's Universal Timing Theory:** According to Gann, financial markets operate in a universe governed by geometric and astrological principles. These cycles repeat themselves over time, and specific days in a given month correspond to key turning points within these repeating cycles. Gann found that the 6th to 7th, 9th to 10th, 14th to 15th, 19th to 20th, 23rd to 24th, and 29th to 31st often marked significant changes in the market, making them particularly important for traders to watch. 3. **Market Psychology and Sentiment:** These specific days likely correspond to key moments where market participants tend to react in predictable ways, influenced by past market behavior on similar dates. For example, news events or scheduled economic reports might fall within these time windows, causing the market to respond in a particular way. Gann's method involves using these cyclical patterns to predict turning points in market prices, enabling traders to anticipate when the market might make a reversal or face a significant shift in direction. 4. **Turning Points:** Gann believed that markets often reversed or encountered critical points around specific dates. This is why he considered certain days more important than others. By identifying and focusing on these days, traders can better anticipate the market’s movement and make more informed trading decisions. 5. **Numerology:** Gann also utilized numerology in his trading system, believing that numbers, and particularly certain key numbers, had significance in predicting market movements. The days selected in this script may correspond to numerological patterns that Gann identified in his analysis of the markets, such as recurring numbers in his astrological and geometric systems. ### **Purpose of the Script:** This script highlights these "Gann Days" within a trading chart for 2024 and 2025. The color-coding or background highlighting is intended to draw attention to these dates, so traders can observe the potential for significant market movements during these times. By identifying these specific dates, traders following Gann's theories may gain insights into possible turning points, corrections, or key price movements based on the market's historical behavior around these days. Overall, Gann’s use of specific days was based on his deep belief in the cyclical nature of the market and his attempt to tie those cycles to the natural laws of time, geometry, and astrology. By focusing on these dates, Gann aimed to give traders an edge in predicting significant market events and price shifts.
Pine Script™ 인디케이터
scott_wyatt14의
Uptrick: Smart BoundariesThis script is an indicator that combines the RSI (Relative Strength Index) and Bollinger Bands to highlight potential points where price momentum and volatility may both be at extreme levels. Below is a detailed explanation of its components, how it calculates signals, and why these two indicators have been merged into one tool. This script is intended solely for educational purposes and for traders who want to explore the combined use of momentum and volatility measures. Please remember that no single indicator guarantees profitable results. Purpose of This Script This script is designed to serve as a concise, all-in-one tool for traders seeking to track both momentum and volatility extremes in real time. By overlaying RSI signals with Bollinger Band boundaries, it helps users quickly identify points on a chart where price movement may be highly stretched. The goal is to offer a clearer snapshot of potential overbought or oversold conditions without requiring two separate indicators. Additionally, its optional pyramiding feature enables users to manage how many times they initiate trades when signals repeat in the same direction. Through these combined functions, the script aims to streamline technical analysis by consolidating two popular measures—momentum via RSI and volatility via Bollinger Bands—into a single, manageable interface. 1. Why Combine RSI and Bollinger Bands • RSI (Relative Strength Index): This is a momentum oscillator that measures the speed and magnitude of recent price changes. It typically ranges between 0 and 100. Traders often watch for RSI crossing into “overbought” or “oversold” levels because it may indicate a potential shift in momentum. • Bollinger Bands: These bands are plotted around a moving average, using a standard deviation multiplier to create an upper and lower boundary. They help illustrate how volatile the price has been relative to its recent average. When price moves outside these boundaries, some traders see it as a sign the price may be overstretched and could revert closer to the average. Combining these two can be useful because it blends two different perspectives on market movement. RSI attempts to identify momentum extremes, while Bollinger Bands track volatility extremes. By looking for moments when both conditions agree, the script tries to highlight points where price might be unusually stretched in terms of both momentum and volatility. 2. How Signals Are Generated • Buy Condition: - RSI dips below a specified “oversold” level (for example, 30 by default). - Price closes below the lower Bollinger Band. When these occur together, the script draws a label indicating a potential bullish opportunity. The underlying reasoning is that momentum (RSI) suggests a stronger-than-usual sell-off, and price is also stretched below the lower Bollinger Band. • Sell Condition: - RSI rises above a specified “overbought” level (for example, 70 by default). - Price closes above the upper Bollinger Band. When these occur together, a label is plotted for a potential bearish opportunity. The rationale is that momentum (RSI) may be overheated, and the price is trading outside the top of its volatility range. 3. Pyramiding Logic and Trade Count Management • Pyramiding refers to taking multiple positions in the same direction when signals keep firing. While some traders prefer just one position per signal, others like to scale into a trade if the market keeps pushing in their favor. • This script uses variables that keep track of how many recent buy or sell signals have fired. If the count reaches a user-defined maximum, no more signals of that type will trigger additional labels. This protects traders from over-committing to one direction if the market conditions remain “extreme” for a prolonged period. • If you disable the pyramiding feature, the script will only plot one label per side until the condition resets (i.e., until RSI and price conditions are no longer met). 4. Labels and Visual Feedback • Whenever a buy or sell condition appears, the script plots a label directly on the chart: - Buy labels under the price bar. - Sell labels above the price bar. These labels make it easier to review where both RSI and Bollinger Band conditions align. It can be helpful for visually scanning the chart to see if the signals show any patterns related to market reversals or trend continuations. • The Bollinger Bands themselves are plotted so traders can see when the price is approaching or exceeding the upper or lower band. Watching the RSI and Bollinger Band plots simultaneously can give traders more context for each signal. 5. Originality and Usefulness This script provides a distinct approach by merging two well-established concepts—RSI and Bollinger Bands—within a single framework, complemented by optional pyramiding controls. Rather than using each indicator separately, it attempts to uncover moments when momentum signals from RSI align with volatility extremes highlighted by Bollinger Bands. This combined perspective can aid in spotting areas of possible overextension in price. Additionally, the built-in pyramiding mechanism offers a method to manage multiple signals in the same direction, allowing users to adjust how aggressively they scale into trades. By integrating these elements together, the script aims to deliver a tool that caters to diverse trading styles while remaining straightforward to configure and interpret. 6. How to Use the Indicator • Configure the Inputs: - RSI Length (the lookback period used for the RSI calculation). - RSI Overbought and Oversold Levels. - Bollinger Bands Length and Multiplier (defines the moving average period and the degree of deviation). - Option to reduce pyramiding. • Set Alerts (Optional): - You can create TradingView alerts for when these conditions occur, so you do not have to monitor the chart constantly. Choose the buy or sell alert conditions in your alert settings. • Integration in a Trading Plan: - This script alone is not a complete trading system. Consider combining it with other forms of analysis, such as support and resistance, volume profiles, or candlestick patterns. Thorough research, testing on historical data, and risk management are always recommended. 7. No Performance Guarantees • This script does not promise any specific trading results. It is crucial to remember that no single indicator can accurately predict future market movements all the time. The script simply tries to highlight moments when two well-known indicators both point to an extreme condition. • Actual trading decisions should factor in a range of market information, including personal risk tolerance and broader market conditions. 8. Purpose and Limitations • Purpose: - Provide a combined view of momentum (RSI) and volatility (Bollinger Bands) in a single script. - Assist in spotting times when price may be at an extreme. - Offer a configurable system for labeling potential buy or sell points based on these extremes. • Limitations: - Overbought and oversold conditions can persist for an extended period in trending markets. - Bollinger Band breakouts do not always result in immediate reversals. Sometimes price keeps moving in the same direction. - The script does not include a built-in exit strategy or risk management rules. Traders must handle these themselves. Additional Disclosures This script is published open-source and does not rely on any external or private libraries. It does not use lookahead methods or repaint signals; all calculations are performed on the current bar without referencing future data. Furthermore, the script is designed for standard candlestick or bar charts rather than non-standard chart types (e.g., Heikin Ashi, Renko). Traders should keep in mind that while the script can help locate potential momentum and volatility extremes, it does not include an exit strategy or account for factors like slippage or commission. All code comes from built-in Pine Script functions and standard formulas for RSI and Bollinger Bands. Anyone reviewing or modifying this script should exercise caution and incorporate proper risk management when applying it to their own trading. Calculation Details The script computes RSI by examining a user-defined number of prior bars (the RSI Length) and determining the average of up-moves relative to the average of down-moves over that period. This ratio is then scaled to a 0–100 range, so lower values typically indicate stronger downward momentum, while higher values suggest stronger upward momentum. In parallel, Bollinger Bands are generated by first calculating a simple moving average (SMA) of the closing price for the user-specified length. The script then measures the standard deviation of closing prices over the same period and multiplies it by the chosen factor (the Bollinger Bands Multiplier) to form the upper and lower boundaries around the SMA. These two measures are checked in tandem: if the RSI dips below a certain oversold threshold and price trades below the lower Bollinger Band, a condition is met that may imply a strong short-term sell-off; similarly, if the RSI surpasses the overbought threshold and price rises above the upper Band, it may indicate an overextended move to the upside. The pyramiding counters track how many of these signals occur in sequence, preventing excessive stacking of labels on the chart if conditions remain extreme for multiple bars. Conclusion This indicator aims to provide a more complete view of potential market extremes by overlaying the RSI’s momentum readings on top of Bollinger Band volatility signals. By doing so, it attempts to help traders see when both indicators suggest that the market might be oversold or overbought. The optional reduced pyramiding logic further refines how many signals appear, giving users the choice of a single entry or multiple scaling entries. It does not claim any guaranteed success or predictive power, but rather serves as a tool for those wanting to explore this combined approach. Always be cautious and consider multiple factors before placing any trades.
Pine Script™ 인디케이터
Uptrick의
1
IPO Lifecycle Sell Strategy [JARUTIR]IPO Lifecycle Sell Strategy with Dynamic Buy Date and Multiple Sell Rules This custom TradingView script is designed for traders looking to capitalize on dynamic strategies for IPOs and growth stocks, by implementing several sell rules based on price action and technical indicators. It provides a set of sell rules that are applied dynamically depending on the stock's lifecycle and price action, allowing users to lock in profits and minimize drawdowns based on key technical thresholds. The four sell strategies incorporated into this script are inspired by the book "The Lifecycle Trade", a resource that focuses on capturing profits while managing risk in different phases of a stock's lifecycle, from IPO to high-growth stages. Key Features: Buy Price and Buy Date: You can either manually input your buy price and date or let the script automatically detect the buy date based on the specified buy price. Multiple Sell Strategies: Choose from 4 predefined sell strategies: Ascender Rule : Captures strong momentum from IPO stocks by selling portions at specific price levels or technical conditions. Midterm Rule : Focuses on holding for longer periods, with defensive sell signals triggered when the stock deviates significantly from peak price or key moving averages. 40 Week Rule : Designed for long-term holds, this rule triggers a sell when the stock closes below the 40-week moving average. Everest Rule : Aggressive strategy for selling into strength based on parabolic moves or gap downs, ideal for high momentum stocks. Interactive Features: Horizontal Green Line showing the buy price level from the buy date. Visual Sell Signals appear only after the buy date to ensure that your analysis is relevant to the stock lifecycle. Customizable settings, allowing you to choose your preferred sell rule strategy and automate buy date detection. This script is perfect for traders using a strategic, systematic approach to IPOs and high-growth stocks, whether you're looking for quick exits during momentum phases or holding for longer-term growth. Usage: Input your Buy Price and Buy Date, or allow the script to automate the buy date detection. Select a Sell Rule strategy based on your risk profile and trading style. View visual signals for selling when specific conditions are met. Frequently Asked Questions (FAQs): Q1: How do I input my Buy Price and Buy Date? The script allows you to either manually input the Buy Price and Buy Date or use the automated detection. If you choose automated detection, the script will automatically assign the buy date when the price crosses above your set Buy Price. Q2: What is the purpose of the "Sell Rules"? The script offers four sell strategies to help manage different types of stocks in varying phases of their lifecycle: Ascender Rule: Targets IPO stocks showing positive momentum. Midterm Rule: A defensive strategy for stocks in a steady uptrend. 40 Week Rule: Long-term hold strategy designed to ride stocks through extended growth. Everest Rule: Aggressive strategy to capture profits during parabolic price moves. Q3: What is the significance of the Green Line at Buy Price? The Green Line represents your entry point (Buy Price) on the chart. It will appear from the buy date onwards, helping you track the performance of your stock relative to your entry. Q4: Can I customize the Sell Strategy? Yes! You can choose from the available Sell Rules (Ascender Rule, Midterm Rule, 40 Week Rule, Everest Rule) via an input option in the script. Each strategy has its own unique triggers based on price action, moving averages, and time-based conditions. Q5: Does this script work for stocks and crypto? Yes, this script is designed for both stocks and cryptocurrencies. It works on any asset where price data and timeframes are available. Q6: How do the Weekly Moving Averages (WSMA) work in this strategy? The script uses weekly moving averages (WSMA) to track longer-term trends. These are essential for some of the sell rules, such as the Midterm Rule and 40 Week Rule, which rely on the stock's movement relative to the 40-week moving average. Q7: Will the script plot a Sell Signal immediately after the Buy Date? No, sell signals will only be plotted after the Buy Date. This ensures that the sell strategy is relevant to your actual holding period and avoids premature triggers. Q8: How do I interpret the Sell Signal? The script will plot a Red Sell Signal above the bar when the sell conditions are met, based on the selected strategy. This indicates that it may be a good time to exit the position according to your chosen rule. Q9: Can I use this strategy on different timeframes? Yes, you can apply the script to any timeframe. However, some sell strategies, like the Midterm Rule and 40 Week Rule, are designed to work best with weekly data, so it's recommended to use these strategies with longer timeframes. Q10: Does this script have any alerts? Yes! The script supports alert conditions that will notify you when the sell conditions are met according to your selected rule. You can set up alerts to stay informed without needing to watch the chart constantly. Q11: What if I want to disable some of the sell rules? You can select your preferred sell rule using the "Select Sell Rule" dropdown. If you don’t want to use a particular rule, simply choose a different strategy or leave it inactive. ------------------------------ Disclaimer: This strategy is intended for educational purposes only. It should not be considered financial advice. Always perform your own research and consult with a professional before making any trading decisions. Trading involves significant risk, and you should never trade with money you cannot afford to lose.
Pine Script™ 인디케이터
JARUTIR의
SMA Proximity Signal with Trend TableSummary of the Script: This Pine Script is designed to provide a variety of technical analysis signals based on Simple Moving Averages (SMAs) and market trends across different timeframes. The script combines multiple indicators, such as the SMA crossover, proximity conditions, and trend analysis, along with visual markers and support/resistance lines. Below is a detailed breakdown of the key features: The script detects crossovers between SMA1 and SMA2 and SMA1 and SMA3, marking them with green circles exactly at the crossover price level (not on the candles). The crossover events are identified using ta.crossover and ta.crossunder functions. Additional circles are drawn when other SMAs are in proximity (narrow stage) Elephant Candle Pattern: The script identifies "Elephant Candles" based on a large candle body relative to the overall size of the candle, using the condition where the candle body is at least 80% of the total candle size and at least 1.5 times the average candle size. These candles are marked with an elephant emoji 🐘 at the top of the candle. Trend Analysis Across Multiple Timeframes: The script calculates the trend for different timeframes using the SMA20 of each timeframe: 5m, 15m, 1h, 4h, and 1D It compares the current SMA20 to its previous value to determine whether the trend is Up, Down, or Flat.
Pine Script™ 인디케이터
alivePlayer23212의
MktCumTickThis script is a market sentiment indicator that calculates the cumulative TICK (Trade Imbalance Sentiment) for four major markets: NYSE (New York Stock Exchange), NASDAQ (National Association of Securities Dealers Automated Quotations), Dow Jones, and AMEX (American Stock Exchange). Here's a breakdown of the script: 1. Market data requests: The script requests data for the four markets, including: - TICK (Trade Imbalance Sentiment) data - HLC3 (High, Low, Close) data - ADVN (Advancing issues), DECL (Declining issues), and UNCH (Unchanged issues) data 2. Cumulative TICK calculation: The script calculates the cumulative TICK for each market by dividing the TICK data by the maximum TICK value for each market. 3. Plotting: The script plots the cumulative TICK values for each market as separate lines on the chart. 4. Background color: The script changes the background color of the chart based on the cumulative TICK values. If all four markets have decreasing cumulative TICK values, the background color turns red. If all four markets have increasing cumulative TICK values, the background color turns green. The purpose of this indicator is to provide a visual representation of market sentiment across multiple markets. By analyzing the cumulative TICK values, traders can gain insights into market trends and make more informed trading decisions. Some possible uses of this indicator include: - Identifying market trends and sentiment - Confirming trade entries and exits - Monitoring market conditions and adjusting trading strategies accordingly
Pine Script™ 인디케이터
OneHolo의
Weekly Bullish Pattern DetectorThis script is a TradingView Pine Script designed to detect a specific bullish candlestick pattern on the weekly chart. Below is a detailed breakdown of its components: 1. Purpose The script identifies a four-candle bullish pattern where: The first candle is a long green (bullish) candlestick. The second and third candles are small-bodied candles, signifying consolidation or indecision. The fourth candle is another long green (bullish) candlestick. When this pattern is detected, the script: Marks the chart with a visual label. Optionally triggers an alert to notify the trader. 2. Key Features Overlay on Chart: indicator("Weekly Bullish Pattern Detector", overlay=true) ensures the indicator draws directly on the price chart. Customizable Inputs: length (Body Size Threshold): Defines the minimum percentage of the total range that qualifies as a "long" candle body (default: 14%). smallCandleThreshold (Small Candle Body Threshold): Defines the maximum percentage of the total range that qualifies as a "small" candle body (default: 10%). Candlestick Property Calculations: bodySize: Measures the absolute size of the candle body (close - open). totalRange: Measures the total high-to-low range of the candle. bodyPercentage: Calculates the proportion of the body size relative to the total range ((bodySize / totalRange) * 100). isGreen and isRed: Identify bullish (green) or bearish (red) candles based on their open and close prices. Pattern Conditions: longGreenCandle: Checks if the candle is bullish (isGreen) and its body percentage exceeds the defined length threshold. smallCandle: Identifies small-bodied candles where the body percentage is below the smallCandleThreshold. consolidation: Confirms the second and third candles are both small-bodied (smallCandle and smallCandle ). Bullish Pattern Detection: bullishPattern: Detects the full four-candle sequence: The first candle (longGreenCandle ) is a long green candle. The second and third candles (consolidation) are small-bodied. The fourth candle (longGreenCandle) is another long green candle. Visualization: plotshape(bullishPattern): Draws a green label ("Pattern") below the price chart whenever the pattern is detected. Alert Notification: alertcondition(bullishPattern): Sends an alert with the message "Bullish Pattern Detected on Weekly Chart" whenever the pattern is found. 3. How It Works Evaluates Candle Properties: For each weekly candle, the script calculates its size, range, and body percentage. Identifies Each Component of the Pattern: Checks for a long green candle (first and fourth). Verifies the presence of two small-bodied candles (second and third). Detects and Marks the Pattern: Confirms the sequence and marks the chart with a label if the pattern is complete. Sends Alerts: Notifies the trader when the pattern is detected. 4. Use Cases This script is ideal for: Swing Traders: Spotting weekly patterns that indicate potential bullish continuations. Breakout Traders: Identifying consolidation zones followed by upward momentum. Pattern Recognition: Automatically detecting a commonly used bullish formation. 5. Key Considerations Timeframe: Works best on weekly charts. Customization: The thresholds for "long" and "small" candles can be adjusted to suit different markets or volatility levels. Limitations: It doesn't confirm the pattern's success; further analysis (e.g., volume, support/resistance levels) may be required for validation
Pine Script™ 인디케이터
dylanhit20의
FVG - NibzDescription: Fair Value Gap (FVG) Indicator - Nibz This Pine Script identifies and visualizes Fair Value Gaps (FVGs) on your TradingView chart. FVGs are price inefficiencies left behind when the market moves too quickly, skipping price levels that might not be tested. These gaps often act as magnets, attracting price for potential reversals or continuations. The script works by detecting upward (bullish) and downward (bearish) price imbalances based on specific candlestick criteria and then marks these zones on your chart using customizable shaded boxes. This tool is essential for traders looking to identify key areas of market inefficiency that could signify support/resistance levels, potential reversal zones, or areas to monitor for market rebalancing. How It Works 1. Bullish FVG Detection The script identifies an upward imbalance when: The low of the candlestick two bars back is less than or equal to the open of the previous bar. The high of the current candlestick is greater than or equal to the close of the previous bar. When this condition is met and the size of the imbalance is greater than zero, a green box is drawn from the low of the second candlestick back to the high of the current candlestick. 2. Bearish FVG Detection The script identifies a downward imbalance when: The high of the candlestick two bars back is greater than or equal to the open of the previous bar. The low of the current candlestick is less than or equal to the close of the previous bar. When this condition is met and the size of the imbalance is greater than zero, a red box is drawn from the low of the current candlestick to the high of the second candlestick back. Customization Options This script is highly customizable, allowing you to tailor the appearance of the FVG boxes to suit your trading style and chart aesthetics: Bullish FVG: Fill color and transparency. Border color and transparency. Bearish FVG: Fill color and transparency. Border color and transparency. The settings are user-friendly, with intuitive sliders for transparency and color pickers for customization. How to Use the Indicator Adding the Script: Add the indicator to your chart, and it will automatically mark bullish (green) and bearish (red) FVGs. Interpreting FVGs: Bullish FVGs (green zones): These often act as support or areas of potential price rebalancing on retracement. Bearish FVGs (red zones): These often act as resistance or areas of interest for short entries. Trade Ideas: Use FVG zones to confirm other trade signals or strategies. Watch for price interaction with these zones to time entries and exits. Key Features Automated detection of Fair Value Gaps. Customizable visual representation to match your chart preferences. Enhances trading precision by identifying price inefficiencies. Suitable for scalping, day trading, or swing trading strategies. This script provides a powerful tool to highlight important price levels and inefficiencies in the market, enabling traders to make informed decisions. Whether you're using it as a standalone indicator or combining it with other tools, the 'FVG - Nibz' indicator is a valuable addition to any trader's toolkit!
Pine Script™ 인디케이터
nibzomatic의
Inside Bar with Swing PointsSwing Points with Inside Bar This script combines swing point analysis with an inside bar pattern visualization, merging essential concepts to identify and visualize key price levels and potential trend reversals. This is especially useful for traders looking to understand price action through swing levels and reactions within inside bar boundaries, making it effective for short-term trend analysis and reversal zone identification. Script Features: Swing Point Analysis: The script identifies swing points based on fractals with a configurable number of bars, allowing for a choice between three and five bars, helping traders fine-tune sensitivity to price movements. Swing points are visualized as labels, highlighting potential reversal or continuation zones in the price chart. Inside Bar Visualization: Inside bars are defined as bars where both the high and low are contained within the previous bar. These often signal consolidation before a potential breakout. The script displays boundaries of the mother bar (the initial bar encompassing inside bars) and colors candles accordingly, highlighting those within these boundaries. This feature helps traders focus on price areas where a breakout or trend shift may occur. Utility and Application: The script enables traders to visualize inside bars and swing points, which is particularly useful for short-term traders focused on reversal or trend continuation strategies. Combining swing point analysis with inside bar identification offers a unique approach, helping traders locate key consolidation zones that may precede significant price moves. This provides not only strong support and resistance levels but also insights into probable breakout points. How to Use the Script: Set the number of bars for swing point analysis (3 or 5) to adjust fractal sensitivity. Enable mother bar boundary visualization and color indication for inside bars to easily spot consolidation patterns. Pay attention to areas with multiple swing points and inside bars, as these often signal potential reversal or breakout zones. This script offers flexible tools for analyzing price movements through both swing analysis and consolidation zone identification, aiding decision-making under uncertainty and enhancing market structure understanding.
Pine Script™ 인디케이터
EK39의
Ultimate Multi-Physics Financial IndicatorThe Ultimate Multi-Physics Financial Indicator is an advanced Pine Script designed to combine various complex theories from physics, mathematics, and statistical mechanics to create a holistic, multi-dimensional approach to market analysis. Let’s break down the core concepts and how they’re applied in this script: 1. Fractal Geometry: Recursive Pattern Recognition Purpose: This part of the script uses fractal geometry to recursively analyze price pivots (highs and lows) for detecting patterns. Fractals: The fractalHigh and fractalLow signals represent key turning points in the market. The script goes deeper by recursively analyzing layers of pivot sequences, adding "depth" to the recognition of patterns. Recursive Depth: It breaks down each detected pivot into smaller components, giving more nuance to market pattern recognition. This provides a broader context for how prices have behaved historically at various levels of recursion. 2. Quantum Mechanics: Adaptive Probabilistic Monte Carlo with Correlation Purpose: This component integrates randomness (from Monte Carlo simulations) with current market behavior using correlation. Randomness Weighted by Correlation: By generating random probabilities and weighting them based on how well the market aligns with recent trends, it creates a probabilistic signal. The random values are scaled by a correlation factor (close prices and their moving average), adding adaptive elements where randomness is adjusted by current market conditions. 3. Thermodynamics: Adaptive Efficiency Ratio (Entropy-Like Decay) Purpose: This section uses principles from thermodynamics, where efficiency in price movement is dynamically adjusted by recent volatility and changes. Efficiency Ratio: It calculates how efficiently the market is moving over a certain period. The "entropy decay factor" reflects how stable the market is. Higher entropy (chaos) results in lower efficiency, while stable periods maintain higher efficiency. 4. Chaos Theory: Lorenz-Driven Market Oscillation Purpose: Instead of using a basic Average True Range (ATR) indicator, this section applies chaos theory (using a Lorenz attractor analogy) to describe complex market oscillations. Lorenz Attractor: This models market behavior with a chaotic system that depends on the historical price changes at different time intervals. The attractor value quantifies the level of "chaos" or unpredictability in the market. 5. String Theory: Multi-Layered Dimensional Analysis of RSI and MACD Purpose: Combines traditional indicators like the RSI (Relative Strength Index) and MACD (Moving Average Convergence Divergence) with momentum for multi-dimensional analysis. Interaction of Layers: Each layer (RSI, MACD, and momentum) is treated as part of a multi-dimensional structure, where they influence one another. The final signal is a blended outcome of these key metrics, weighted and averaged for complexity. 6. Fluid Dynamics: Adaptive OBV (Pressure-Based) Purpose: This section uses fluid dynamics to understand how price movement and volume create pressure over time, similar to how fluids behave under different forces. Adaptive OBV: Traditional OBV (On-Balance Volume) is adapted by using statistical smoothing to measure the "pressure" exerted by volume over time. The result is a signal that shows where there might be building momentum or pressure in the market based on volume dynamics. 7. Recursive Synthesis of Signals Purpose: After calculating all the individual signals (fractal, quantum, thermodynamic, chaos, string, and fluid), the script synthesizes them into one cohesive signal. Recursive Feedback Loop: Each signal is recursively influenced by others, forming a feedback loop that allows the indicator to continuously learn from new data and self-adjust. 8. Signal Smoothing and Final Output Purpose: To avoid noise in the output, the final combined signal is smoothed using an Exponential Moving Average (EMA), which helps stabilize the output for easier interpretation. 9. Dynamic Color Coding Based on Signal Extremes Purpose: Visual clarity is enhanced by using color to highlight different levels of signal strength. Color Coding: The script dynamically adjusts colors (green, orange, red) based on the strength of the final signal relative to its percentile ranking in historical data, making it easier to spot bullish, neutral, or bearish signals. The "Ultimate Multi-Physics Financial Indicator" integrates a diverse array of scientific principles — fractal geometry, quantum mechanics, thermodynamics, chaos theory, string theory, and fluid dynamics — to provide a comprehensive market analysis tool. By combining probabilistic simulations, multi-dimensional technical indicators, and recursive feedback loops, this indicator adapts dynamically to evolving market conditions, giving traders a holistic view of market behavior across various dimensions. The result is an adaptive and flexible tool that responds to both short-term and long-term market changes
Pine Script™ 인디케이터
Cmo22의
2
Saturn Retrograde PeriodsSaturn Retrograde Periods Visualizer for TradingView This Pine Script visualizes all Saturn retrograde periods since 2009, including the current retrograde ending on November 15, 2024. The script overlays yellow boxes on your TradingView chart to highlight the exact periods of Saturn retrograde. It's a great tool for astrologically-inclined traders or those interested in market timing based on astrological events. Key Features: Full Historical Coverage: Displays Saturn retrograde periods from 2009 (the inception of Bitcoin) to the current retrograde ending in November 2024. Customizable Appearance: You can easily adjust the color and opacity of the boxes directly from the script's settings window, making it flexible for various chart styles. Visual Clarity: The boxes span the full vertical range of your chart, ensuring the retrograde periods are clearly visible over any asset, timeframe, or price action. How to Use: Add the script to your TradingView chart. Adjust the color and opacity in the settings to suit your preferences. View all relevant Saturn retrograde periods and analyze how these astrological events may align with price movements in your selected asset. This script is perfect for traders and analysts who want to combine astrology with financial market analysis! scripted by chat.gpt - version 1.0
Pine Script™ 인디케이터
cryptos4oats의
Set Alarm for Closed Codes [Mr_Rakun]Set Alarm for Closed Codes This Pine Script code is designed to set up alerts based on two types of conditions: Crossover or Greater-Lesser thresholds. The script's most significant feature is its ability to set alerts using external sources that the user defines for long and short positions. These sources can be any other indicator or value on the chart, giving traders maximum flexibility in choosing their alert triggers. Crossover Condition: The script triggers an alert when the closing price crosses above or below the user-defined external sources for long and short signals. Greater-Lesser Condition: It also allows triggering alerts when the defined input values (like 70 for greater, 30 for lesser) are crossed by the external sources. Users can input the message for buy and sell signals (such as "BUY" or "SELL") and set custom thresholds to create more flexible alerts based on market behavior. The code also visually plots the user-selected entry sources on the chart, with the short entry source being displayed in red for easier identification. In summary, the key feature of this script is its ability to set alerts based on external sources defined by the user, making it highly versatile for traders who want to automate alerts for specific price movements or indicator-based conditions. -------------------------------------------------- Türkçe Açıklama Bu Pine Script kodu, iki farklı koşula dayalı olarak alarm kurmayı amaçlar: Kesişim veya Büyük-Küçük eşikleri. Kodun en önemli özelliği, uzun ve kısa pozisyonlar için kullanıcı tarafından tanımlanan dış kaynaklar kullanılarak alarm kurulabilmesidir. Bu kaynaklar, grafikteki herhangi bir gösterge veya değer olabilir, bu da yatırımcılara alarm tetikleyicilerini seçmede maksimum esneklik sağlar. Kesişim Koşulu: Kapanış fiyatı, kullanıcı tarafından tanımlanan dış kaynakları geçtiğinde uzun veya kısa sinyaller için alarm tetiklenir. Büyük-Küçük Koşulu: Ayrıca, belirlenen giriş değerlerinin (örneğin, büyük için 70, küçük için 30) dış kaynaklarla kesişmesi durumunda alarm tetiklenir. Kullanıcılar, alış ve satış sinyalleri için mesajlar (örneğin, "AL" veya "SAT") girebilir ve piyasa hareketlerine dayalı olarak daha esnek alarmlar oluşturmak için özel eşikler belirleyebilir. Kod, ayrıca grafik üzerinde kullanıcı tarafından seçilen giriş kaynaklarını da çizer; kısa giriş kaynağı kırmızı renkte gösterilir, böylece kolayca tanımlanabilir. Özetle, bu scriptin ana özelliği, kullanıcı tarafından tanımlanan dış kaynaklara dayalı alarm kurabilme yeteneği olup, belirli fiyat hareketleri veya gösterge tabanlı koşullar için alarm kurmak isteyen yatırımcılar için oldukça esnektir.
Pine Script™ 인디케이터
Mr_Rakun의
1
EV Calculator [CHE]EV Calculator with Adjustable Boxes and Custom Colors for TradingView Introduction: As a trader, one of the key metrics you need to evaluate is the Expected Value (EV) of your trading strategy. Understanding EV helps you gauge whether your trades will be profitable in the long run. This TradingView script allows you to visualize your EV alongside customizable win rates and risk-to-reward ratios. With adjustable visual components, you can quickly determine whether your trading strategy has a positive or negative EV, and make informed decisions. Features of the Script: 1. Customizable Inputs: - Win Rate: Set your win probability (0.0 to 1.0), which represents how often your strategy is successful. - Risk and Reward: Define how much you're risking and the potential reward for each trade. 2. Visual Representation: - The script creates colored boxes representing different EV scenarios: - Green Box: Indicates a good EV (>2), suggesting a highly profitable strategy. - Yellow Box: Represents a neutral EV (between 0 and 2), where the strategy could work but is not optimal. - Red Box: Shows a negative EV (<0), signaling that the strategy may lead to losses. 3. Adjustable Box Size: - You can modify the width and height of the boxes to fit your chart display preferences, giving you better visual clarity based on your screen or chart style. 4. Dynamic Labels: - Each bar in the chart includes dynamic labels showing: - Win Rate: Displays the percentage chance of success. - EV Value: Shows the calculated expected value based on the win rate and risk-reward ratio. - Guide: Explains what each colored box means so that you can easily interpret the chart. 5. Scalability and Flexibility: - The script only keeps a maximum of 20 recent entries, ensuring that your chart stays clean and organized. - Both the number of labels and boxes adjust automatically to match your preferred settings, enhancing usability. How the EV Calculation Works: The formula for EV is based on a standard risk-to-reward model: EV = (Win\ Rate \times Reward) - (Loss\ Probability \times Risk) For example: - If your win rate is 60% and your risk-to-reward ratio is 1:3, the script will calculate whether this strategy is expected to yield positive returns or result in long-term losses. Example Use Case: Let's say you are trading with a 60% win rate, risking 1 unit to gain 3 units. The script calculates that your EV is positive and represents this with a Green Box, showing you that your strategy has a high likelihood of being profitable. If your strategy slips and the win rate drops, the EV calculation will adjust, and you may see Yellow or Red Boxes, signaling a need for adjustment. Final Thoughts: This script is designed for traders who want to take their analysis beyond the basics. By providing real-time visualization of your EV, you can better assess whether your strategy is sound and make adjustments as needed. How to Use: - Adjust the input parameters for Win Rate, Risk, and Reward to match your trading strategy. - Observe the colored boxes and labels to quickly understand if your current strategy is in a healthy EV zone. - Use this visual feedback to refine your approach and stay on track towards profitability. This tool simplifies the complex calculations behind EV and turns it into an intuitive and powerful decision-making aid for traders. Now you're ready to integrate the EV Calculator with Adjustable Boxes and Custom Colors into your trading routine and start optimizing your strategies for long-term success! Happy Trading and best regards Chervolino
Pine Script™ 인디케이터
chervolino의
Landry Light with Moving AverageLandry Light with Moving Average Overview: This Pine Script, titled "Landry Light with Moving Average", visualizes the relationship between price action and a chosen moving average (MA) over time. It helps users easily identify periods where the price stays consistently above or below the moving average, which can be a useful indicator of bullish or bearish trends. Key Features: Moving Average Type Selection: The script allows users to choose between two types of moving averages: Exponential Moving Average (EMA) Simple Moving Average (SMA) This is done via a user input option, enabling traders to tailor the indicator to their preferred analysis method. Moving Average Length: Users can set the length of the moving average (default is 21 periods). This allows customization based on the trader's time frame, whether short-term or long-term analysis. Dynamic Moving Average Color: The moving average line changes color based on the relationship between the price and the MA: Green: Price is consistently above the MA (bullish condition). Red: Price is consistently below the MA (bearish condition). Blue: Price is crossing or close to the MA (neutral or indecisive condition). Cumulative Days Above/Below MA: The script tracks and displays the number of consecutive days the price remains above or below the moving average: Cumulative Days Above: Shown as a green histogram above the zero line. Cumulative Days Below: Shown as a red histogram below the zero line. This feature helps users identify sustained trends or potential reversals. Real-time Labels: The script generates dynamic labels that display the count of cumulative days the price has stayed above or below the moving average. These labels are positioned near the moving average on the chart, providing an easy reference for traders. How Users Can Benefit: Trend Identification: By visually representing how long the price stays above or below a key moving average, traders can identify strong bullish or bearish trends. This can inform entry and exit points. Visualizing Market Sentiment: The colored moving average line and histogram help traders quickly assess market sentiment. A prolonged green MA line suggests a strong uptrend, while a prolonged red line indicates a downtrend. Adaptability: With customizable moving average types and lengths, the indicator can be tailored to fit various trading strategies, whether for day trading, swing trading, or long-term investing. Reversal Signals: A shift from cumulative days above to cumulative days below (or vice versa) can serve as an early signal of a potential market reversal, allowing traders to adjust their positions accordingly. Simplified Decision-Making: The combination of visual cues (colors, histograms, and labels) simplifies decision-making, allowing traders to focus on trend strength rather than complex calculations. Usage: To use this script: Add the Indicator to Your Chart: Select the desired moving average type and length. The script will plot the moving average, colored by the trend, and display cumulative days above or below it. Interpret the Signals: Use the histogram and labels to gauge the strength of the trend. Monitor color changes in the moving average for potential trend reversals. Incorporate into Your Strategy: Combine this indicator with other tools (e.g., volume analysis, RSI) to confirm signals and refine your trading strategy. This indicator is particularly useful for traders who follow the "Landry Light" concept, emphasizing the importance of price staying above or below a moving average to determine trend strength.
Pine Script™ 인디케이터
starshiptrade의
Normalized and Smoothed Cumulative Delta for Top 5 NASDAQ StocksThis script is designed to create a TradingView indicator called **"Normalized and Smoothed Cumulative Delta for Top 5 NASDAQ Stocks."** The purpose of this indicator is to track and visualize the cumulative price delta (the change in price from one period to the next) for the top five NASDAQ stocks: Apple Inc. (AAPL), Microsoft Corporation (MSFT), Alphabet Inc. (GOOGL), Amazon.com Inc. (AMZN), and Meta Platforms Inc. (FB). ### Key Features of the Script: 1. **Ticker Selection**: - The script focuses on the top five NASDAQ stocks by automatically setting their tickers. 2. **Price Data Retrieval**: - It fetches the closing prices for each of these stocks using the `request.security` function for the current timeframe. 3. **Delta Calculation**: - The script calculates the delta for each stock, which is simply the difference between the current closing price and the previous closing price. 4. **Cumulative Delta Calculation**: - It calculates the cumulative delta for each stock by adding the current delta to the previous cumulative delta. This helps track the total change in price over time. 5. **Summing and Smoothing**: - The cumulative deltas for all five stocks are summed together. - The script then applies an Exponential Moving Average (EMA) with a period of 5 to smooth the summed cumulative delta, making the indicator less sensitive to short-term fluctuations. 6. **Normalization**: - To ensure the cumulative delta is easy to interpret, the script normalizes it to a range of 0 to 1. This is done by tracking the minimum and maximum values of the smoothed cumulative delta and scaling the data accordingly. 7. **Visualization**: - The normalized cumulative delta is plotted as a smooth line, allowing users to see the overall trend of the cumulative price changes for the top five NASDAQ stocks. - A horizontal line is added at 0.5, serving as a midline reference, which can help traders quickly assess whether the normalized cumulative delta is above or below its midpoint. ### Usage: This indicator is particularly useful for traders and investors who want to monitor the aggregated price movements of the top NASDAQ stocks, providing a high-level view of market sentiment and trends. By smoothing and normalizing the data, it offers a clear and concise visualization that can be used to identify potential market turning points or confirm ongoing trends.
Pine Script™ 인디케이터
spiritedDirect61073의